Evaluating rules applied to data

ABSTRACT

Specifying rules for processing data included in fields of elements of a dataset includes rendering user interface elements associated with a respective condition. The user interface elements include: first subsets of user interface elements, at least some of which are associated with an input value derived from at least one field, and second subsets of user interface elements, each configured to receive user input associated with a respective condition. Conditions are applied to at least a first element of the dataset based on user input received from at least some of the user interface elements, in response to receiving user input for a first user interface element associated with a first field. Instructions are generated for applying one or more selected conditions associated with fewer than all of the user interface elements, the selected conditions including at least a condition associated with the first user interface element.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Application Ser. No.61/883,399, filed on Sep. 27, 2013, incorporated herein by reference.

BACKGROUND

This description relates to evaluating rules applied to data.

Rules can be used, for example, for converting data from one format toanother, making determinations about data, or generating new data basedon a set of input data. Rules for making various decisions (sometimescalled “business rules”) can determine output data to generate oractions to perform based on input data. A more detailed explanation ofbusiness rules can be found in U.S. Pat. No. 8,069,129, EDITING ANDCOMPILING BUSINESS RULES, which is incorporated herein by reference.

SUMMARY

In one aspect, in general, a computing system specifies one or morerules for processing data included in one or more fields of each elementof a plurality of elements of a dataset. The computing system includes auser interface module configured to render a plurality of user interfaceelements associated with a respective condition. The user interfaceelements include: one or more first subsets of the user interfaceelements, at least some subsets of the one or more first subsetsassociated with an input value derived from at least one field of anelement of the plurality of elements of the dataset, and multiple secondsubsets of the user interface elements, each user interface element ofone or more of the multiple second subsets configured to receive userinput associated with a respective condition. The computing systemincludes a processing module configured to apply conditions to at leasta first element of the dataset based on user input received from atleast some of the user interface elements, in response to receiving userinput for a first user interface element associated with a first field.Applying the conditions includes: generating instructions for applyingone or more selected conditions associated with fewer than all of theuser interface elements, the selected conditions including at least acondition associated with the first user interface element, andexecuting the generated instructions and providing feedback associatedwith a result based on applying the condition associated with the firstuser interface element to data included in the first field of the firstelement.

Aspects can have one or more of the following features.

The user interface elements are included in cells arranged in a gridhaving a first axis and a second axis, the one or more first subsets ofthe user interface elements are included in respective subsets of thecells extending in a direction along the first axis of the grid, and themultiple second subsets of the user interface elements are included inrespective subsets of the cells extending in a direction along thesecond axis of the grid.

The processing module is further configured to: generate a specificationof an evaluation order for conditions associated with different cells;and execute the generated instructions for applying the selectedconditions according to the specification of the evaluation order, andprovide feedback associated with results in response to applying theselected conditions to data included in one or more fields of the firstelement according to the specification of the evaluation order.

The specification of the evaluation order includes a state transitiondiagram that includes states representing different conditions andincludes transitions among the states that define an order in which theconditions are allowed to be applied.

Applying the conditions further includes: storing the generatedinstructions; and executing the stored generated instructions to applythe condition associated with the first user interface element to dataincluded in the first field of a second element.

Applying the conditions further includes: storing the result based onapplying the condition associated with the first user interface elementto data included in the first field of the first element; and retrievingthe stored result in response to applying the condition associated withthe first user interface element to data included in the first field ofa second element that is the same as data included in the first field ofthe first element.

The one or more subsets of the cells extending in a direction along thefirst axis are columns of cells.

The multiple subsets of the cells extending in a direction along thesecond axis are rows of cells.

The result of applying the condition to the data included in the firstfield of the element includes a pass/fail result.

The providing feedback includes applying shading to the first userinterface element if the result is a fail result.

Applying the conditions further includes providing feedback associatedwith applying conditions associated with one or more cells to dataincluded in multiple elements of the dataset.

The processing module is further configured to validate a syntax of acondition.

The at least some cells associated with a field and a validation ruleprovide feedback associated with the result of the validation of thesyntax of the condition.

The dataset includes one or more tables of a database and the elementsof the dataset include database records.

Generating instructions for applying one or more conditions associatedwith fewer than all of the user interface elements includes generatinginstructions for applying selected conditions associated with respectiveuser interface elements, the selected consisting of a conditionassociated with the first user interface element and one or moreadditional conditions selected based on information specifying potentialdependencies between different conditions.

In another aspect, in general, a computing system specifies one or morerules for processing data included in one or more fields of each elementof a plurality of elements of a dataset. The computing system includesmeans for rendering a plurality of user interface elements associatedwith a respective condition. The user interface elements include: one ormore first subsets of the user interface elements, at least some subsetsof the one or more first subsets associated with an input value derivedfrom at least one field of an element of the plurality of elements ofthe dataset, and multiple second subsets of the user interface elements,each user interface element of one or more of the multiple secondsubsets configured to receive user input associated with a respectivecondition. The computing system includes means for applying conditionsto at least a first element of the dataset based on user input receivedfrom at least some of the user interface elements, in response toreceiving user input for a first user interface element associated witha first field. Applying the conditions includes: generating instructionsfor applying one or more selected conditions associated with fewer thanall of the user interface elements, the selected conditions including atleast a condition associated with the first user interface element, andexecuting the generated instructions and providing feedback associatedwith a result based on applying the condition associated with the firstuser interface element to data included in the first field of the firstelement.

In another aspect, in general, a method for specifying one or more rulesfor processing data included in one or more fields of each element of aplurality of elements of a dataset includes: rendering a plurality ofuser interface elements associated with a respective condition, the userinterface elements including one or more first subsets of the userinterface elements, at least some subsets of the one or more firstsubsets associated with an input value derived from at least one fieldof an element of the plurality of elements of the dataset, and multiplesecond subsets of the user interface elements, each user interfaceelement of one or more of the multiple second subsets configured toreceive user input associated with a respective condition; and applyingconditions to at least a first element of the dataset based on userinput received from at least some of the user interface elements, inresponse to receiving user input for a first user interface elementassociated with a first field, where applying the conditions includesgenerating instructions for applying one or more selected conditionsassociated with fewer than all of the user interface elements, theselected conditions including at least a condition associated with thefirst user interface element, and executing the generated instructionsand providing feedback associated with a result based on applying thecondition associated with the first user interface element to dataincluded in the first field of the first element.

In another aspect, in general, software stored in a non-transitory formon a computer-readable medium, for specifying one or more rules forprocessing data included in one or more fields of each element of aplurality of elements of a dataset, the software includes instructionsfor causing a computing system to: render a plurality of user interfaceelements associated with a respective condition, the user interfaceelements including one or more first subsets of the user interfaceelements, at least some subsets of the one or more first subsetsassociated with an input value derived from at least one field of anelement of the plurality of elements of the dataset, and multiple secondsubsets of the user interface elements, each user interface element ofone or more of the multiple second subsets configured to receive userinput associated with a respective condition; and apply conditions to atleast a first element of the dataset based on user input received fromat least some of the user interface elements, in response to receivinguser input for a first user interface element associated with a firstfield, where applying the conditions includes generating instructionsfor applying one or more selected conditions associated with fewer thanall of the user interface elements, the selected conditions including atleast a condition associated with the first user interface element, andexecuting the generated instructions and providing feedback associatedwith a result based on applying the condition associated with the firstuser interface element to data included in the first field of the firstelement.

In another aspect, in general, a computing system specifies one or morerules for processing data included in one or more fields of each elementof a plurality of elements of a dataset. The computing system includes auser interface module configured to render a plurality of user interfaceelements associated with a respective condition. The user interfaceelements include: one or more first subsets of the user interfaceelements, at least some subsets of the one or more first subsetsassociated with an input value derived from at least one field of anelement of the plurality of elements of the dataset, and multiple secondsubsets of the user interface elements, each user interface element ofone or more of the multiple second subsets configured to receive userinput associated with a respective condition. The computing systemincludes a processing module configured to apply conditions to at leasta first element of the dataset based on user input received from atleast some of the user interface elements, in response to receiving userinput for a first user interface element associated with a first field.Applying the conditions includes: generating computer executableinstructions for applying selected conditions associated with respectiveuser interface elements, the selected conditions being a conditionassociated with the first user interface element and one or moreadditional conditions selected based on information specifying potentialdependencies between different conditions, and executing the generatedinstructions and providing feedback associated with a result based onapplying the condition associated with the first user interface elementto data included in the first field of the first element of the dataset.

Aspects can include one or more of the following advantages.

In some systems, the process of editing and testing rules can behindered by the inefficiencies of preparing the edited rules forexecution. For example, a rule specification that specifies variousconditions that make up a rule may be stored in a format that issuitable for making rule modifications based on user input. But, thatrule specification may need to be compiled into an executable form(e.g., computer executable instructions) before the rules can beefficiently applied to input data. Additionally, in order to facilitatethe development of rules by users who may be experts in a field forwhich the rules are being used but not expert computer programmers, itis helpful to provide a relatively short delay between the time a rulespecification is edited and the time the specified rule is ready fortesting on test input data. A rule compilation procedure that isefficient and responsive to a user's input within a rules editorinterface enables certain technical problems hindering such ruledevelopment to be overcome.

The system described herein is able to efficiently compile instructionsfor applying a rule in response to receiving user input. For example,the user input may be associated with editing a portion of a rulespecification. The system is able to selectively re-compile instructionsfor portions of the rule specification without having to re-compileinstructions for the entire rule specification. This selectivity enablesefficient feedback for rule editing. For example, a rule may bespecified using various conditions expressed by different logicalexpressions. When a user enters an expression, compiled instructions forevaluating that expression can be generated and saved. Results ofapplying those expressions to input data can be displayed within aneditor. Some of the expressions may depend on results of otherexpressions. Results of applying expressions to input data (includingresults of other expressions), or results of evaluating expressions thatdo not depend on input data, can also be saved. The entire rulespecification can be evaluated again after a user edits a particularexpression by re-compiling that expression and selectively re-executingsaved instructions for expressions whose input values may have beenaffected by the user edit. A lineage representation of an order in whichexpressions are evaluated can be used to determine those expressionsthat are potentially dependent on the edited expression. If anexpression is determined to be not affected by an edit, then its savedresults can be used without having to re-compile or re-evaluate thatexpression.

Other features and advantages of the invention will become apparent fromthe following description, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of a system for evaluating rules applied todata.

FIG. 2A is a user interface for specifying rules for analyzing data.

FIG. 2B is a user interface for specifying rules for analyzing dataincluding user feedback.

FIG. 2C illustrates the user interface of FIG. 2B with a modified rulecase.

FIG. 3 is a screen capture of the user interface for specifying rules.

FIG. 4A is a lineage diagram for efficiently compiling and applyingrules.

FIG. 4B is a user interface for a rule of the lineage diagram.

FIGS. 4C and 4D are state transition diagrams for the rule of FIG. 4B.

DESCRIPTION

FIG. 1 shows an exemplary data processing system 100 in which the ruleevaluation techniques can be used. The system 100 includes a data source102 that may include one or more sources of data such as storage devicesor connections to online data streams, each of which may store data(sometimes referred to as a “dataset”) in any of a variety of storageformats (e.g., database tables, spreadsheet files, flat text files, or anative format used by a mainframe). An execution environment 104includes a user interface (UI) module 106 and a processing module 108.The UI module 106 manages input received from a user 110 over a userinterface 112 (e.g., a graphical view on a display screen) forspecifying rules to be used by the processing module 108 for processingdata from the data source 102.

The execution environment 104 may be hosted on one or moregeneral-purpose computers under the control of a suitable operatingsystem, such as the UNIX operating system. For example, the executionenvironment 104 can include a multiple-node parallel computingenvironment including a configuration of computer systems using multiplecentral processing units (CPUs), either local (e.g., multiprocessorsystems such as SMP computers), or locally distributed (e.g., multipleprocessors coupled as clusters or MPPs), or remote, or remotelydistributed (e.g., multiple processors coupled via a local area network(LAN) and/or wide-area network (WAN)), or any combination thereof.

The processing module 108 reads data from the data source 102 andevaluates rules applied to the data based on a rule specificationdefined by input obtained by the UI module 106. In preparation forevaluating a rule, the processing module 108 generates an evaluationorder that defines at least a partial ordering among multiple ruleconditions of the rule specification, as described in more detail below.The evaluation order can be represented, for example, as a statetransition diagram that determines an order in which different ruleconditions will be evaluated. Storage devices providing the data source102 may be local to the execution environment 104, for example, beingstored on a storage medium connected to a computer running the executionenvironment 104 (e.g., hard drive 114), or may be remote to theexecution environment 104, for example, being hosted on a remote system(e.g., mainframe 116) in communication with a computer running theexecution environment 104, over a remote connection.

In general, a dataset accessed from the data source 102 includes anumber of data elements (e.g., records formatted according to apredetermined record structure, or rows in a database table). Eachelement of the number of data elements can include values for a numberof fields (e.g., attributes defined within a record structure, orcolumns in a database table) (e.g., “first name,” “last name,” “emailaddress,” etc.), possibly including null or empty values. Variouscharacteristics of values in the fields (e.g., related to content ordata type), or the presence or absence of values in certain fields, maybe considered valid or invalid. For example, a “last name” fieldincluding the string “Smith” may be considered valid, while a “lastname” field that is blank may be considered invalid.

Some rules can be applied to test for valid values or othercharacteristics of the data values. The performance of an applicationthat utilizes a dataset from the data source 102 may be adverselyaffected if the dataset includes a significant number of data elementswith one or more invalid fields. The processing module 108 may applydata validation rules to the dataset, to ensure that the dataset meets aquality constraint defined by validation rules. The data processingsystem 100 alerts a system administrator if the quality of the datasetfails to meet the quality constraint. In some examples, the processingmodule 108 may be configured to repair invalid data, if possible, orperform various data cleansing procedures to generate a dataset ofcleansed data elements. In yet other examples, the processing module 108may be configured to generate a list of fields that include invalid datafrom which reports can be generated. In some examples, the reportsinclude a count of records that included invalid data for one or more ofthe fields in the list of fields. In other examples, aggregations ofinvalid fields are calculated from the list of fields.

In general, different applications process different types of data.Thus, depending on the application, the elements of the dataset mayinclude different fields. The UI module 106 provides the user interface112, which enables a set of rules to be specified and used to processthe dataset. The user interface 112 is able to provide a single viewincluding multiple fields of a particular data element structure (insome implementations, all the available fields). Thus, for a givenapplication, the user 110 (e.g., a system administrator) is able tospecify appropriate validation rules for the data.

In some systems, rules are applied to data to validate data according tocertain standards of data quality. Many modern applications, includingbusiness applications, process large sets of data (i.e., “datasets”),which may be compiled from various sources. The various sources thatprovide data to the dataset may have different levels of data quality.To ensure that the applications function properly, an adequate level ofdata quality in the dataset should be maintained. To maintain anadequate level of data quality, the dataset can be processed by a datavalidation system. Such a system applies validation rules to the datasetbefore it is provided to the application. In some examples, the datavalidation system uses the results of validation rules to calculate ameasure of data quality and alert an administrator of the application ifthe measure of data quality falls below a predetermined threshold. Inother examples, the data validation system includes modules for handlingdata that fails one or more of the validation rules. For example, thedata validation system may discard or repair data that fails one or moreof the validation rules. In general, the validation rules applied by thedata validation system are defined by an administrator of the datavalidation system.

In some systems, rules are applied to data to make decisions (e.g.,business decisions) based on the content of the data. For example, arecord in a flight reservation system may indicate the name of apassenger, how many miles the passenger has flown this year, the classof their ticket, and the row they are seated in. A business rule can beconfigured to indicate that such a passenger should be put in boardinggroup 1. A business rule is generally easy for a human to understand,i.e., “first class passengers are in group 1,” but may need to betranslated into something a computer can understand before it can beused to manipulate data.

An interface for editing validation rules or business rules or otherrules may incorporate features to efficiently generate instructions forapplying a rule, enabling efficient feedback for rule editing. Tosimplify creation of rules for non-technical users, an interface isprovided for such users to specify a set of rules, referred to as a ruleset, in a format with which they are familiar. A rule set is the set ofrules that are to be applied to a dataset (e.g., the validation rulesdefined based on user input in a user interface). A rule within a ruleset may be composed of one or more rule cases that compute differentvalues for the rule's output depending on the input. A rule may alsoreference other rules, for example, by referencing values computed byother rules.

Referring to FIG. 2A, one example of the user interface is a rule grid212 configured to facilitate the user 110 specifying one or more rulesfor processing the data included in one or more fields of each elementof the dataset.

The UI module 106 renders the user interface 212 (e.g., on a computermonitor) using a number of cells 224 arranged in a two-dimensional grid225 having a first axis 226 and a second axis 228. In this example, eachcell of the user interface 212 is configured to receive input, such astext, entered by a user (e.g., using a text input field, or other typeof user interface element). One or more subsets of the cells (referredto as columns or trigger columns 232 in the remainder of the detaileddescription) extends in a direction along the second axis 228 of thetwo-dimensional grid 225. Each of the trigger columns 232 can optionallybe associated with an input value derived from data in a data elementsuch as a value from a field of a data element of the dataset, orderived from other sources. For example, the input value associated witha trigger column can also reference values computed by other rules(e.g., intermediate values and/or output values), or values from anotherdata source or from user input, or any combination of these. In someexamples, the first (i.e., the topmost) cell of each of the columns 232includes the name of a field 218 or other source of an input value 242associated with the trigger column 232. The user interface 212 is alsoconfigured to display the input value 242 associated with the triggercolumn 232 for the element currently selected in the user interface 212.

Multiple subsets 230 of the cells 224 (referred to as rows or rule caserows 230 in the remainder of the detailed description) extend in adirection along the first axis 226 of the two dimensional grid 225. Oneor more of the rule case rows 230 is associated with a respective set ofconditions that relate to the available input values associated with thetrigger columns 232. It is noted that in some examples, the directionsof the first axis 226 and the second axis 228 can be swapped, causingthe columns 232 associated with the input values to become rows 230, andthe rows 230 associated with the rule condition 236 to become columns232. Alternatively, other groupings of the subsets of cells (or otheruser interface elements) corresponding to a rule case may not use a gridarrangement, and may instead use different screen regions (e.g.,windows) that are arranged or selectively presented in responds to usernavigation, for example.

To apply a rule to one or more data elements, the processing module 108is able to generate a state transition diagram (or other representationof the evaluation order) for the rule based on the arrangement of therows and columns within the grid, as described in more detail below. Theprocessing module 108 uses the state transition diagram to successivelyevaluate rule conditions of the rule case rows until a rule case issatisfied. A rule case specified in a given rule case row 230 issatisfied for a given data element if the input values 242 derived fromthat data element, for each trigger column 232 in which the rule casehas a condition, meet the triggering conditions (i.e., a rule case thathas all of its conditions on input values satisfied may be referred toas “triggered”). If a rule case 230 is triggered, output is generatedbased on one or more output columns 250. In some implementations, theevaluation of rule case rows stops after the first rule case hastriggered. Each output column 250 may correspond to a potential outputvariable, and the output column value in the corresponding cell of theapplicable row 230 determines the output, if any, for that variable. Thecell could contain a value that is assigned to the variable or it couldcontain an expression that must be evaluated to generate the outputvalue, as discussed below. There may be more than one output column,though only one is shown in FIG. 2A.

While the resemblance of a grid of rule case rows to a spreadsheet mayaid in a user's ability to visualize a rule, the implicit dependenciesamong cells based on their arrangement within the grid is different fromthe explicit dependencies between cells in a spreadsheet and the othercells that they reference. For example, in some implementations, whetherthe rule conditions of a rule case row are even evaluated depends onwhether a rule case above that rule row has already been triggered.

There may be several different types of trigger columns 232 with cellsthat correspond to different kinds of conditions. Some trigger columns(e.g., “comparison columns”) can include cells that define a value orrange of values that are compared to the input value associated withthat trigger column, and the result of the comparison evaluates to trueor false. Some trigger columns (e.g., “free-form columns”) are notassociated with an input value, and instead include cells that define acondition that evaluates to true or false without requiring comparisonto an input value. Thus, each non-empty cell defines (explicitly orimplicitly) a condition that evaluates to true or false, whether thecondition is dependent on a data element or not. Free-form triggercolumns can include cells that contain, for example, one of thefollowing:

-   -   An expression. The condition will be considered to be true if        the evaluation of the expression evaluates to a non-zero,        non-NULL value.    -   The keyword “any,” or an empty string. The condition is always        true. Each empty cell in a trigger column is equivalent to one        explicitly containing the keyword “any.”    -   The keyword “else.” The condition is true if none of the cells        above the cell containing “else” and below any empty cells are        true, in rows where all cells to the left are identical.    -   The keyword “same”. The condition is true if the cell above is        true.

Comparison columns can include two types of cells. One type of cell isan expression cell. Those cells behave exactly like cells in a free-formcolumn, described above. However, the keyword “this” can be used in theexpression to refer to the column input value. The other type of cell isa comparison cell that defines a value or range of values to be comparedto the input value associated with the column. An exemplary grammar forcomparison cells is as follows:

operator ::= “>” | “<” | “>=” | “<=” | “!=” | “=” | “equals”value_element ::= constant | constant | variable | “(“expression “)”value_expression ::= [ operator ] value_element simple_function ::=“is_null” | “is_blank” | “is_valid” | “is_defined” | “is_bzero”membership_expr ::= “in” “[“ value_element ( ( “,” | “to” | “or” )  value_element)* “]” simple_value ::= [ “not” ] ( value_expression |simple_function |   membership_expr ) compound_value ::= simple_value (“and” simple_value )* comparison_value ::= compound_value ( “or”compound_value )*where a “*” means a term is repeated zero or more times. If no operatoris specified in a cell, a default operator such as “equals” can beimplied.

Any suitable programming language or syntax may be used. Examples mayinclude C, Java, Prolog. In some implementations, the programminglanguage can be a data manipulation language (DML) that also includessyntax for defining data formats and manipulating data using variousdata processing operations.

To evaluate a comparison cell for a given trigger column, the value 242associated with the column 232 is compared against the comparison cellvalue or range according to the operator, function, or membershipexpression. In the example of FIG. 2A, the first two trigger columns 232a, 232 b contain comparison cells with the “>=” operator, thus thecondition is met if the value for that column is greater than or equalto the corresponding number. If there is no operator, as in the ‘SeatClass’ column 232 c, then “equals” is assumed. A constant can be anylegal constant in whatever programming language or syntax is used in theunderlying system. The other constants and variable are business termsas defined within the rule set, as described below. An expression is anylegal expression in the language being used that returns a compatibledata type that will be compared against the column input value. In someexamples, expressions inside comparison cells are enclosed inparenthesis to avoid ambiguity. For the simple_function, the function isapplied to the column input value, so the “is_null” keyword is the sameas the expression “is_null(this)”.

In the example of FIG. 2A, the first row 230 a has a condition in onlyone column (i.e., ‘Total Frequent Flyer Miles’ column 232 a), whichindicates that if the total number of frequent flyer miles for atraveler is greater than 1,000,000, then that rule case appliesregardless of what value any other columns may have. In that case, the“Boarding Group” output variable for that user is set to group 1.Likewise, the second rule case 230 b indicates that any flier in firstclass is in group 1. In some examples, the rules are evaluated in order,so a traveler having over 1,000,000 miles and a first class ticket willbe in group 1, but only the first rule case will be triggered. Once arule case is triggered, the other rule cases in that rule do not need tobe evaluated.

The third rule case 230 c is based on two input values (i.e., valuesassociated with the ‘Total Frequent Flyer Miles’ and ‘Current FrequentFlyer Miles’ columns 232 a, 232 b)—if the conditions defined for bothtotal frequent flier miles and current-year miles are met, then theflier is in group 2. In the fourth rule case 230 d, any business classcustomers are also in group 2. The remaining rule cases 230 e-230 gcontain conditions that relate to the other rule cases, i.e., “else” and“same.” As discussed above, the keyword “else” indicates that none ofthe conditions in that trigger column were met in rows that were abovethat one and below any empty cells and which had the same condition tothe left, which in this example means the seat class is not “Business.”The keyword “same” indicates that the rule case applies if the rule caseabove it applied with respect to that trigger column. Thus, each of theremaining rule cases 230 e-230 g applies to data elements that didn'tmatch any higher rule case, and which have the appropriate “seat row”value.

In some examples, the rule cases 230 a-g in the example of FIG. 2A canalso be represented as individual simple rules, each in their own grid(not shown). A user could create these individual rules separately,rather than generating the entire table shown in FIG. 2A.

In some examples, the editor interface shown in FIG. 2A may graphicallyidentify cells that contain expressions, and may graphically distinguishbetween an expression that will be evaluated to true or false on its ownand an expression that returns a value that is compared against thecolumn input value. When the user 110 is typing, they can indicate thata particular cell is to be an expression cell by, for example, typing anasterisk at the beginning.

In some examples, values and expressions are DML expressions. Thespecial keywords and the business names for fields and values areencoded as strings that are pre-processed out of the DML expressions.Note that the expressions can use the logical (business) names forvariables, but can also refer to the actual physical names.

For columns that correspond to output variables, the cells can contain,for example, one of the following:

-   -   A value. The value that will be assigned to the output variable    -   An expression. The value of the expression is assigned to the        output variable. If the expression evaluates to NULL then the        field gets the NULL value, unless the output field is        not-nullable. In which case, an error is generated.    -   The keyword “null”. If the output field is nullable, then the        field will be assigned NULL. Otherwise, an error is generated.    -   An empty string. If the output field has a default value, then        the default value is assigned. Otherwise, the cell is treated as        if it contains the keyword “null”.    -   The keyword “same”. The output field is assigned the same value        computed in the cell above.

If possible, errors are reported as soon as possible (e.g., putting“null” in an output for a non-nullable field). However, some errors arenot reported until either test-time or run-time.

In addition to expressions, users may be allowed to attach comments toany cell in the rule. The comments can be displayed like commentsattached to cells in spreadsheet programs such as Microsoft Excel.

In some examples, the rules editor interface may be configured torestrict what a user may enter more tightly than the technicalrequirements of the interface would require. For example, the interfacemay be configured to only allow certain types of input values or certaintypes of expressions in order to provide a simpler, more constraineduser interface. The interface may also be configured to restrict whichcells in a rule can be changed, based on a user's role or user ID. Suchrestrictions may be applied to a rule set by an administrator.

Rules can be defined based on a rule grid in various ways when theprocessing module 108 evaluates a rule. In some examples, rules may beevaluated in a manner converse to that described above, with rule casesin rows being ANDed and columns being ORed. That is, a rule produces anoutput only if every row triggers (ANDing the rows) but only a singlecell needs to be true for each row to trigger (ORing the columns).

A more detailed explanation of the rules grid can be found in U.S. Pat.No. 8,069,129, EDITING AND COMPILING BUSINESS RULES, which isincorporated herein by reference.

Referring to FIG. 2B, the user interface 212 of FIG. 2A can be augmentedto provide feedback to the user 110. In particular, each of the cells ofthe two-dimensional grid 225 is configured to indicate whether the rulecondition 236 for the cell passed or failed for an element 244 currentlyselected by the user interface 112. In some examples, the pass/failindication is provided to the user 110 by shading cells that failedtheir associated rule condition 236. For example, the cell associatedwith the first rule case 230 a and the first trigger column 232 aincludes a rule condition that returns a pass result if the value 242 ofthe field 218 associated with the first trigger column 232 a (i.e., the‘Total Frequent Flyer Miles’ trigger column) is greater than or equal to1,000,000. From inspection, one can see that the actual value 242 of thefield 218 associated with the first trigger column 232 a is 750,000which is less than 1,000,000. Thus, the rule condition 236 fails and thecell associated with the first rule case 230 a and the first triggercolumn 232 a is shaded to indicate the failed result. Various othercells are shaded in the figure, indicating that they include failed ruleconditions. Output cells in the output column 250 are shaded if thatrule case row has at least one failed rule condition. Thus, the firstnon-shaded output cell would correspond to the rule case that istriggered. The user 110 can utilize the feedback to ensure that thespecified rules are functioning as expected.

In some examples, the user 110 can navigate through the elements of thedataset using a navigation control 246. In some examples, navigationcontrol 246 includes arrows, which allow the user 110 to step throughthe elements of the dataset one at a time and a numeric field, whichallows the user 110 to enter a dataset element number that they wouldlike to view. Whenever the user 110 navigates to a different elementusing the navigation control 246, the processing module 108 executes thespecified rule cases on the values of the newly selected element.

In some examples, the user interface includes a test control 248, whichpermits the processing module 108 to apply the specified rule cases toall of the elements of the dataset. Upon completion of applying the rulecases to the dataset, the processing module 108 provides the results ofapplying the rule cases to the dataset to the UI module 106, which inturn displays the results in the user interface 212 to the user 110. Forexample, the number of elements for which a rule case triggered can bedisplayed in the user interface 212. The results can be compared againstpreviously stored baseline results generated, for example, from adifferent version of the same rule cases or a different set of rulecases or rules applied by a different system. A set of filtered dataelements can also be presented along with the results applying the rulecases to all of the data elements of the dataset. For example, thefilter may display only those elements for which there is somedifference in results compared to the baseline results, or the filtermay display only those elements for which a particular expression istrue (or false) or for which a particular rule or rule case wastriggered (or not triggered). In some examples, a summary of the resultsare displayed to the user in a separate user interface (not shown).

In some examples, the feedback described above can be provided as a ruleis being edited within the user interface 212. The UI module 106provides information entered into the cells of the user interface 212 tothe processing module 108 to apply the edited rule condition within arule case row to the corresponding value 242 of the trigger column 232.The processing module 108 uses the techniques described herein toselectively determine which other rule conditions should be applied tothe respective values of their trigger columns.

In some examples, when a rule case is added, removed, or any of itscells are modified by the user 110 through the user interface 212, theUI module 106 passes the changes to the processing module 108, whichre-applies the changed rule conditions, and any other rule conditionsthat come after those rule conditions in an evaluation order, asdescribed in more detail below. If a rule case is added or any of itscells are modified, the processing module 108 is configured to apply thenewly added or modified rule case to at least one element of thedataset. In some examples, the added or modified rule case is appliedonly to the element of the dataset that is current displayed in the userinterface 212. The result of applying the added or modified rule caseand any other selected rule cases are then passed to the UI module 106,which in turn updates the user interface 212 to display the results. Forexample, if the newly added or modified rule case includes a condition236 that produced a failed result for the element of the dataset, thecell including the condition 236 is shaded to indicate the failedresult. Conversely, if the newly added or modified rule case includes acondition 236 that produced a passing result for the element of thedataset, the cell including the condition 236 is not shaded, indicatinga passing result.

Due to potential dependencies between the rule conditions, changing onerule condition may affect the results of other rule conditions that maydepend on the result of the changed rule condition since they areevaluated after that rule condition. Thus, in some examples, theprocessing module 108 is configured to re-apply all rule conditions thatare ordered after a newly added, removed, or modified rule condition ina determined evaluation order. The results of re-applying those selectedrule conditions are also displayed to the user on the user interface212.

Referring to FIG. 2C, the user 110 has modified the cell associated withthe first rule case 230 a and the first trigger column 232 a through theuser interface 212 of FIG. 2B. In particular, the cell is changed toindicate that the rule condition associated with the cell is satisfiedif the value of the ‘Total Frequent Flyer Miles’ is greater than orequal to 500,000 rather than the previous value of 1,000,000.

Modifying the first rule case 230 a causes the processing module 108 tore-apply the rule case for the currently selected element. Since thevalue of the ‘Total Frequent Flyer Miles’ field for the currentlyselected element is 750,000, a passing result for the modified cell ofthe first rule case 230 a is returned by the processing module 108 anddisplayed as an un-shaded cell by the user interface 212. Since thefirst rule case passed the ‘Boarding Group’ output value changes to 1.In this example, none of the other rule cases have conditions that needto be re-applied.

In the following example, the processing module 108 will selectivelydetermine which rule cases are to be re-applied for efficientre-evaluation of the rule cases after a user edits a cell. Theprocessing module 108 generates (e.g., compiles) executable instructionsfor applying each rule condition as a function of any input values onwhich the condition depends, such as the value 242 associated with atrigger column, or values associated with other cells. The executableinstructions, the input values, and the results of applying thoseexecutable instructions to those input values can be stored for lateruse, along with information specifying potential dependencies betweendifferent rule conditions based on an order of evaluation for those ruleconditions.

Referring to FIG. 3, a screen capture 300 illustrates one implementationof the user interface 212 of FIGS. 2A-2C. The user interface implementedin the screen capture 300 is configured to allow a user 110 to specifyrules for a dataset while receiving feedback from application of thoserules to that dataset (or a different test dataset).

As is described above for the user interface 212, the user interfaceillustrated in the screen capture 300 includes a two-dimensional grid ofcells. The grid includes a number of rows, each row associated with arule case. The grid also includes a number of trigger columns. The nameof each input value is included at the top of each of the columns (e.g.,“Avg Monthly Balance,” Avg Monthly Charges,” etc.). This exampleincludes a custom trigger column 320, where each cell is not limited toproviding a rule condition for a common input value, but rather for anycomputed value (such as “Airplane Ticket Buys” for rule case row 8, or“Restaurant Meal Buys” for rule case row 9).

In this example, the user 110 has specified a number of rule caseconditions, each associated with a respective rule case and a triggercolumn. To do so, the user 110 selects a cell and enters an expressioninto the selected cell. For example, in the figure, the user 110 hasselected a cell 302 at the intersection of the row associated with the8^(th) rule case and the column associated with the “Avg MonthlyCharges” field and has entered the expression “>=5000.” The expressionentered into the selected cell indicates that the rule case only passesfor a given data element if the value of the “Avg Monthly Charges” fieldfor the data element is greater than or equal to 5000. The current valueof the “Avg Monthly Charges” field for the data element currentlyselected in the navigation control 304 is displayed in the triggercolumn heading 306. If the number of the selected data element ischanged (e.g., from “1” to “2”), the processing module 108 does notnecessarily need to re-compile and re-evaluate all of the ruleconditions from all of the cells. For example, for cells that have notbeen edited when the next data element is selected, the stored compiledinstructions for the rule conditions in those cells can be retrieved andre-executed on new input values for the next data element. Furthermore,if an input value for a particular trigger column for the next dataelement is the same as the input value for that particular triggercolumn for the previous data element (e.g., “Years as Customer” has thesame value “21”), then the stored results for the rule conditions inthose cells can be retrieved and re-used without even needing tore-execute the compiled instructions.

Feedback can be provided within the user interface, as the user editsthe cells, about whether or not particular cells' conditions aresatisfied. Different colors can indicate different results. One colorcan be used to indicate that a cell's condition is not satisfied, andanother color can be used for an entire rule case row for which all ofthe cells' conditions are satisfied (as they are for the 8^(th) rulecase in FIG. 3), in which case that rule case will be triggered when therule is run on the selected data element.

Referring to FIGS. 4A-4C, after an expression is entered into a selectedcell of a rule being edited, in response to the user 110 completing theediting (e.g., by de-selecting the cell or navigating to another cell)the processing module 108 selectively re-applies rule conditions basedon a specification of potential dependencies between different ruleconditions associated with different cells of the edited rule or otherrules in the same rule set as the edited rule, as represented, forexample, by a lineage diagram 400 (FIG. 4A) and a state transitiondiagram 430 (FIG. 4D). The nodes 402A-402J in the lineage diagram 400Arepresent values (field values or other input values, output variables,and/or other variables storing values used in the computation), and thenodes 404A-404D represent rules that each includes any number of rulecases. Together the rules represented by the nodes 404A-404D maycorrespond to an entire rule set, for example. The node 404B in thediagram 400 represents the rule with the edited rule condition. Thelineage diagram 400 and state transition diagram 430 represent an orderin which rules and rule conditions, respectively, are evaluated. Thus,the potential dependencies specified by this type of specification of anevaluation order are due to the potential for later-evaluated items tobe dependent upon results of earlier evaluated items. These dependenciesare thus potential dependencies in the sense that it is possible that alater-evaluated (“downstream”) item is not affected by anearlier-evaluated (“upstream”) item.

FIG. 4B shows a simplified example of such a rule 410. The rule 410includes three rule case rows for rule conditions on input values A andB of two trigger columns, and an output variable V of a single outputcolumn. A state transition diagram 420 representing an order in whichthe different rule conditions may be evaluated is shown in FIG. 4C. Eachstate corresponds to evaluation of a particular rule condition for aparticular cell of the rule 410. The transitions correspond to a resultof the evaluation being either true (T) or false (F). Such a statetransition diagram 420 can be generated, for example by providing achain of states connected by T links for the cells in each row, with Flinks from each state in the chain going to the first state in the chainof states for the next row. This technique for generating a statetransition diagram corresponds to an evaluation order that depends onthe order of trigger columns. Improvements in the efficiency of ruleevaluation represented by the state transition diagram can be made bychanging the order of trigger columns, or even by removing certainredundant states. For example, FIG. 4D shows a state transition diagram430 that removes a state representing a rule condition that does notneed to be evaluated since it has already been evaluated previously inthe same diagram 430. The links to and from the removed state can alsobe removed, with links of other states being modified to provide thesame functionality. Even with the modifications to improve efficiency,the state transition diagram may not represent the optimum order ofevaluation. However, even if the state transition diagram issub-optimal, the techniques described herein of selectivelyre-evaluating rule conditions during editing can still result inefficient updating of the rules editor interface.

When only a single cell's rule condition has changed, the processingmodule 108 only has to re-compile the edited cell's rule condition togenerate executable instructions for applying the rule condition. Theprocessing module 108 executes those re-compiled instructions and alsoexecutes previously stored compiled instructions for applying ruleconditions that occur later in the evaluation order than the rulecondition associated with the edited cell. So selected rule conditions“downstream” of the edited rule condition may be re-evaluated, but notrule conditions “upstream” of the edited rule condition. In thisexample, if the rule condition that determines whether or not the valueof the input B is equal to 2 (corresponding to the state labeled “B==2”in the state transition diagram 420) was just edited, the processingmodule 108 will re-compile the instructions for that state and then willcontinue execution from that state, executing downstream rule conditionsas needed, depending on the results of each rule condition. Theprocessing module 108 will also selectively re-evaluate values and ruleconditions of other rules based on their relationship to the edited rule404B in the evaluation order, i.e., according to the lineage diagram400. So, in this example, the values 402H and 402J, and the ruleconditions of rule 404D, which are all downstream of the edited rule404B will be re-evaluated, and the other values and rules do not need tobe re-evaluated since they are not downstream of (i.e., later in theevaluation order) the edited rule 404B.

Feedback can then be provided in response to selectively applying thosedownstream rule conditions to input data according to the evaluationorder as represented by the lineage diagram 400 and the state transitiondiagram 430. The results of the execution are passed back to the UImodule 106 for display in the user interface. Feedback to the user isprovided to the user 110 by shading any cells that include a failed rulecondition and not shading cells that include a passing rule condition.The implementation of the user interface illustrated by the screencapture 300 includes a number of shaded cells (which were shaded afterre-application of the rule conditions), which indicate that the rulecondition specified in that shaded cell has failed for the currentlyselected data element. The user interface also includes a control 308 toinitiate generation of a lineage diagram, showing the relationshipsbetween the rule being edited and input and output values and otherrules, to be presented in a user interface window.

In some implementations, the processing module 108 selectivelyre-compiles rule conditions more often than is strictly necessary basedon a trade-off between resources needed to manage the executableinstructions for different cells and resources needed to perform there-compilation. In some situations (e.g., for a simple set of rules withrelatively few cells), rule conditions even for cells that have not beenedited may be re-compiled. Furthermore, the processing module 108 maynot need to store dependency information tracking dependencies betweendifferent sets of complied instructions (generated after the initialcompilation or after re-compilation) for those situations in whichediting cells will always result in re-compilation of all cells.

In general, when the set of rules specified in the user interface isapplied to a data element, the first rule case (i.e., the rule casespecified in the first row of rule cases) is evaluated against thevalues of the fields of the data element. If all of the conditions ofthe first rule case are satisfied, then the output of the rule set is aset of outputs 310 associated with the first rule case. If any of theconditions of the first rule case are not satisfied, then the secondrule case (i.e., the rule case specified in the second row of rulecases) is evaluated against the values of the fields of the dataelement. If all of the conditions of the second rule case are satisfied,then the output of the rule set is a set of outputs 312 associated withthe second rule case. This evaluation process continues until set ofoutputs is determined. Visually, the rule case associated with theoutput case includes no failed rule conditions, and therefore includesno shaded cells.

As is noted above, the user 110 can navigate through the elements of thedataset using a navigation control 304. Whenever the user 110 navigatesto a different element using the navigation control 304, the UI module106 executes the specified rule cases on the values of the newlyselected element.

Furthermore, the user interface includes a test control 314, whichpermits the UI module 106 to apply the specified rule cases to all ofthe elements of the dataset. Upon completion of applying the rule casesto the dataset, the processing module 108 provides the results ofapplying the rule cases to the dataset to the UI module 108, which inturn displays the results in the user interface to the user 110. In someexamples, a summary of the results are displayed to the user in aseparate user interface (not shown).

Various alternative implementations can be used. For example, while theabove description describes providing feedback to users by shadingcells, other types of feedback mechanisms (e.g., sounds, pop-up windows,special symbols, etc.) can be utilized. The above description describesspecifying rules while working on a full dataset. However, in someexamples, a test dataset that has a reduced and more manageable size andis representative of a full dataset can be used.

The techniques described above can be implemented, for example, using aprogrammable computing system executing suitable software instructionsor it can be implemented in suitable hardware such as afield-programmable gate array (FPGA) or in some hybrid form. Forexample, in a programmed approach the software may include procedures inone or more computer programs that execute on one or more programmed orprogrammable computing system (which may be of various architecturessuch as distributed, client/server, or grid) each including at least oneprocessor, at least one data storage system (including volatile and/ornon-volatile memory and/or storage elements), at least one userinterface (for receiving input using at least one input device or port,and for providing output using at least one output device or port). Thesoftware may include one or more modules of a larger program, forexample, that provides services related to the design, configuration,and execution of dataflow graphs. The modules of the program (e.g.,elements of a dataflow graph) can be implemented as data structures orother organized data conforming to a data model stored in a datarepository.

The software may be provided on a tangible, non-transitory medium, suchas a CD-ROM or other computer-readable medium (e.g., readable by ageneral or special purpose computing system or device), or delivered(e.g., encoded in a propagated signal) over a communication medium of anetwork to a tangible, non-transitory medium of a computing system whereit is executed. Some or all of the processing may be performed on aspecial purpose computer, or using special-purpose hardware, such ascoprocessors or field-programmable gate arrays (FPGAs) or dedicated,application-specific integrated circuits (ASICs). The processing may beimplemented in a distributed manner in which different parts of thecomputation specified by the software are performed by differentcomputing elements. Each such computer program is preferably stored onor downloaded to a computer-readable storage medium (e.g., solid statememory or media, or magnetic or optical media) of a storage deviceaccessible by a general or special purpose programmable computer, forconfiguring and operating the computer when the storage device medium isread by the computer to perform the processing described herein. Theinventive system may also be considered to be implemented as a tangible,non-transitory medium, configured with a computer program, where themedium so configured causes a computer to operate in a specific andpredefined manner to perform one or more of the processing stepsdescribed herein.

A number of embodiments of the invention have been described.Nevertheless, it is to be understood that the foregoing description isintended to illustrate and not to limit the scope of the invention,which is defined by the scope of the following claims. Accordingly,other embodiments are also within the scope of the following claims. Forexample, various modifications may be made without departing from thescope of the invention. Additionally, some of the steps described abovemay be order independent, and thus can be performed in an orderdifferent from that described.

What is claimed is:
 1. A computing system for specifying one or morerules for processing data included in one or more fields of each elementof a plurality of elements of a dataset, the computing system including:a user interface module configured to render a plurality of userinterface elements associated with a respective condition, the userinterface elements including one or more first subsets of the userinterface elements, at least some subsets of the one or more firstsubsets associated with an input value derived from at least one fieldof an element of the plurality of elements of the dataset, and multiplesecond subsets of the user interface elements, each user interfaceelement of one or more of the multiple second subsets configured toreceive user input associated with a respective condition; and aprocessing module configured to apply conditions to at least a firstelement of the dataset based on user input received from at least someof the user interface elements, in response to receiving user input fora first user interface element associated with a first field, whereapplying the conditions includes generating instructions for applyingone or more selected conditions associated with fewer than all of theuser interface elements, the selected conditions including at least acondition associated with the first user interface element, andexecuting the generated instructions and providing feedback associatedwith a result based on applying the condition associated with the firstuser interface element to data included in the first field of the firstelement.
 2. The system of claim 1, wherein the user interface elementsare included in cells arranged in a grid having a first axis and asecond axis, the one or more first subsets of the user interfaceelements are included in respective subsets of the cells extending in adirection along the first axis of the grid, and the multiple secondsubsets of the user interface elements are included in respectivesubsets of the cells extending in a direction along the second axis ofthe grid.
 3. The system of claim 2, wherein the processing module isfurther configured to: generate a specification of an evaluation orderfor conditions associated with different cells; and execute thegenerated instructions for applying the selected conditions according tothe specification of the evaluation order, and provide feedbackassociated with results in response to applying the selected conditionsto data included in one or more fields of the first element according tothe specification of the evaluation order.
 4. The system of claim 3,wherein the specification of the evaluation order includes a statetransition diagram that includes states representing differentconditions and includes transitions among the states that define anorder in which the conditions are allowed to be applied.
 5. The systemof claim 2, wherein applying the conditions further includes: storingthe generated instructions; and executing the stored generatedinstructions to apply the condition associated with the first userinterface element to data included in the first field of a secondelement.
 6. The system of claim 2, wherein applying the conditionsfurther includes: storing the result based on applying the conditionassociated with the first user interface element to data included in thefirst field of the first element; and retrieving the stored result inresponse to applying the condition associated with the first userinterface element to data included in the first field of a secondelement that is the same as data included in the first field of thefirst element.
 7. The system of claim 2, wherein the one or more subsetsof the cells extending in a direction along the first axis are columnsof cells.
 8. The system of claim 2, wherein the multiple subsets of thecells extending in a direction along the second axis are rows of cells.9. The system of claim 2, wherein the result of applying the conditionto the data included in the first field of the element includes apass/fail result.
 10. The system of claim 9, wherein the providingfeedback includes applying shading to the first user interface elementif the result is a fail result.
 11. The system of claim 2, whereinapplying the conditions further includes providing feedback associatedwith applying conditions associated with one or more cells to dataincluded in multiple elements of the dataset.
 12. The system of claim 2,wherein the processing module is further configured to validate a syntaxof a condition.
 13. The system of claim 12, wherein the at least somecells associated with a field and a validation rule provide feedbackassociated with the result of the validation of the syntax of thecondition.
 14. The system of claim 1, wherein the dataset includes oneor more tables of a database and the elements of the dataset includedatabase records.
 15. The system of claim 1, wherein generatinginstructions for applying one or more conditions associated with fewerthan all of the user interface elements includes generating instructionsfor applying selected conditions associated with respective userinterface elements, the selected consisting of a condition associatedwith the first user interface element and one or more additionalconditions selected based on information specifying potentialdependencies between different conditions.
 16. A computing system forspecifying one or more rules for processing data included in one or morefields of each element of a plurality of elements of a dataset, thecomputing system including: means for rendering a plurality of userinterface elements associated with a respective condition, the userinterface elements including one or more first subsets of the userinterface elements, at least some subsets of the one or more firstsubsets associated with an input value derived from at least one fieldof an element of the plurality of elements of the dataset, and multiplesecond subsets of the user interface elements, each user interfaceelement of one or more of the multiple second subsets configured toreceive user input associated with a respective condition; and means forapplying conditions to at least a first element of the dataset based onuser input received from at least some of the user interface elements,in response to receiving user input for a first user interface elementassociated with a first field, where applying the conditions includesgenerating instructions for applying one or more selected conditionsassociated with fewer than all of the user interface elements, theselected conditions including at least a condition associated with thefirst user interface element, and executing the generated instructionsand providing feedback associated with a result based on applying thecondition associated with the first user interface element to dataincluded in the first field of the first element.
 17. A method forspecifying one or more rules for processing data included in one or morefields of each element of a plurality of elements of a dataset, themethod including: rendering a plurality of user interface elementsassociated with a respective condition, the user interface elementsincluding one or more first subsets of the user interface elements, atleast some subsets of the one or more first subsets associated with aninput value derived from at least one field of an element of theplurality of elements of the dataset, and multiple second subsets of theuser interface elements, each user interface element of one or more ofthe multiple second subsets configured to receive user input associatedwith a respective condition; and applying conditions to at least a firstelement of the dataset based on user input received from at least someof the user interface elements, in response to receiving user input fora first user interface element associated with a first field, whereapplying the conditions includes generating instructions for applyingone or more selected conditions associated with fewer than all of theuser interface elements, the selected conditions including at least acondition associated with the first user interface element, andexecuting the generated instructions and providing feedback associatedwith a result based on applying the condition associated with the firstuser interface element to data included in the first field of the firstelement.
 18. Software stored in a non-transitory form on acomputer-readable medium, for specifying one or more rules forprocessing data included in one or more fields of each element of aplurality of elements of a dataset, the software including instructionsfor causing a computing system to: render a plurality of user interfaceelements associated with a respective condition, the user interfaceelements including one or more first subsets of the user interfaceelements, at least some subsets of the one or more first subsetsassociated with an input value derived from at least one field of anelement of the plurality of elements of the dataset, and multiple secondsubsets of the user interface elements, each user interface element ofone or more of the multiple second subsets configured to receive userinput associated with a respective condition; and apply conditions to atleast a first element of the dataset based on user input received fromat least some of the user interface elements, in response to receivinguser input for a first user interface element associated with a firstfield, where applying the conditions includes generating instructionsfor applying one or more selected conditions associated with fewer thanall of the user interface elements, the selected conditions including atleast a condition associated with the first user interface element, andexecuting the generated instructions and providing feedback associatedwith a result based on applying the condition associated with the firstuser interface element to data included in the first field of the firstelement.